\f0\b0\i0\outl0\shad0\fs36 \cf0 \expan0 \ul0 Compiling\f0\b0\i0\outl0\shad0\fs36 \cf0 \expan0 \ul0 \line \f0\b0\i0\outl0\shad0\fs28 \cf1 \expan0 \ul0 \line Now that you\u8217've got all routines sorted out to pop up in the menu, and have all \u8216'\f0\b0\i0\outl0\shad0\fs28 \cf2 \expan0 \ul0 ;\f0\b0\i0\outl0\shad0\fs28 \cf1 \expan0 \ul0 \u8217' and \u8216'\f0\b0\i0\outl0\shad0\fs28 \cf2 \expan0 \ul0 )\f0\b0\i0\outl0\shad0\fs28 \cf1 \expan0 \ul0 \u8217' and \u8216'\f0\b0\i0\outl0\shad0\fs28 \cf2 \expan0 \ul0 {\f0\b0\i0\outl0\shad0\fs28 \cf1 \expan0 \ul0 \u8216' and switches taken care of, it\u8217's time to get it to compile in C. \line \line In Think C, I use \u8220"Check Syntax\u8221" on the file, rather than \u8220"Run\u8221" or \u8220"Compile.\u8221" That way I don\u8217't have to deal with the error window. No need to try to compile or run when you KNOW it won\u8217't do either, at this point! The error window will only give you the first error anyway.\line \line \f0\b0\i0\outl0\shad0\fs28 \cf3 \expan0 \ul0 C\f0\b0\i0\outl0\shad0\fs28 \cf2 \expan0 \ul0 Tools\f0\b0\i0\outl0\shad0\fs28 \cf2 \expan0 \ul0 \u8482?\f0\b0\i0\outl0\shad0\fs28 \cf1 \expan0 \ul0 only marks some things which the user may or may not want done a certain way. The first of these is \u8220"Includes:\u8221" - the carry-over from Pascals \u8220"Uses\u8221" line.\line \line My \f0\b0\i0\outl0\shad0\fs28 \cf4 \expan0 \ul0 KodeKeys\f0\b0\i\outl0\shad\fs28 \cf1 \expan0 \ul0 macros can help, here. Hit \f0\b0\i0\outl0\shad0\fs28 \cf5 \expan0 \ul0 ctrl-i\f0\b0\i0\outl0\shad0\fs28 \cf1 \expan0 \ul0 for \f1\b0\i0\outl0\shad0\fs20 \cf2 \expan0 \ul0 #include <.h>\f0\b0\i0\outl0\shad0\fs28 \cf1 \expan0 \ul0 or \f0\b0\i0\outl0\shad0\fs28 \cf5 \expan0 \ul0 ctrl-option-i\f0\b0\i0\outl0\shad0\fs28 \cf1 \expan0 \ul0 for \f1\b0\i0\outl0\shad0\fs20 \cf2 \expan0 \ul0 #include \u8220".h\u8221"\f0\b0\i0\outl0\shad0\fs28 \cf1 \expan0 \ul0 , then just paste in the name of the header included.\line \line Add the appropriate include directives and comment out or cut out the \u8220"dead\u8221" code. Pascal includes (uses) some of its own source files. C does not usually do this. So, in the \u8220".p\u8221" file, which once may have said \u8220"Uses MyMenus.p\u8221", it does not, now, need \u8220"#include \u8220"MyMenus.p.c\u8221". Dig? C only wants header data. If there is \u8220"header stock\u8221" in the \u8220"MyMenus.p.c\u8221" file that IS needed by another c. file, then cut it and put it in a seperate header.\line \line For the rest of the file, you may want to consult the Pascal original for comparisons - especially if an omission is suspected. Also, compare forms of what\u8217's translated to comparable things in working C sources. From that, a good \u8220"source detective\u8221" should be able to get a correct translation where \f0\b0\i0\outl0\shad0\fs28 \cf3 \expan0 \ul0 C\f0\b0\i0\outl0\shad0\fs28 \cf2 \expan0 \ul0 Tools\f0\b0\i0\outl0\shad0\fs28 \cf2 \expan0 \ul0 \u8482?\f0\b0\i0\outl0\shad0\fs28 \cf1 \expan0 \ul0 falls down.\line \line }
